Reset mnesia run at from last run #1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Recalculating
run_at(expressed in monotonic time) at boot time for Mnesia module. This is for fixing issue koudelka#99.Since we don't know which FailureMode we are using, we cannot recalculate the
run_atin the Mnesia module. Thus, we need to store the last time that the Job was run (in system time). I have added alast_runfield in the WrapperJob to track this. The drawback of this approach is that if the user wants to use this patch, he will need to drain his queues, before making the upgrade.